Divisions: I am afraid that it would be very difficult to bring them back. I will discuss on Monday with the team, if we could find any good alternatives.

Forcefield password: They are not being transferred to other pilots. We are currently changing the way of how this is being enforced (Probably by storing the password on the character and not on the ship).

Separate access options for SMB and Fleet hangar: I will discuss this on Monday with the team.

"Will we be able to drop items *into* a fleet hangar if the box isn't checked?" - No, you will be unable to open the fleet hangar.

Hey all,

Short update: We had some discussions today, but our programmer for these changes was not in the office today, so we have to wait with any decisions. I'll post here as soon as anything is decided.

A short explanation for the fleet hangar changes from my point of view: Why are doing this and removing a feature (divisions)?
The concept of having corp hangars on personal ships had some benefits, but it was a constant source of bugs and inconsistencies and it made changes to related features more difficult. For many players (and devs ) it was also quite confusing which rules and roles apply exactly in which case. After quite some internal whining about bugs and inconsistencies it was decided to rework the whole system and convert the corporation hangars into fleet hangars - with the goal to improve the experience for all players. Unfortunately we underestimated the current usage of the corp hangars - so we need to fix this part.

Hey folks.

Being the guy writing this code, I think I should chime in a bit (disclaimer: I haven't read through the whole thread yet).

The corp hangars on ships code had to go. Sorry, but that's simply the reality of the matter. It's been broken since it was first put in the game and was made completely unfixable when fleet member access was added to the mix. And by broken I mean both design and implementation. Corp roles clashed and were inconsistent between usages, there was no way for the client to reliably know if it could access another players ship so it had to guess and handle errors (you can probably imagine how healthy and correct that was most of the time), you could put stuff in without knowing that you couldn't take it back and the list just kept growing. Every time someone fixed a bug in this code, at least two new bugs surfaced, usually within either POS corp hangar arrays or offices in stations as all 3 of them shared the same codebase. It. Had. To. Go.

So, taking as a given that we could no longer use the same code for the ships corp hangars as the other types, then the options really boil down to either a) rewrite the corp hangars on ships seperetaly, but keep the corp hangars concept, but not share the code with the other two types of corp hangars, or b) rethink the functionality. Having two almost identical corp-hangars implementations, except for a bunch of special cases, didn't ring particularly well with the engineer in me and having to construct some resemblance of sanity and to avoid code-duplication, either through inheritance or composition while doing it wasn't appealing either.

So, after asking around, both internally, via the CSM and within the player community where I know people, it was generally agreed that fleet hangars were the way to go.

I'm absolutely not dismissing any of your criticisms here, merely explaining why a change had to happen. We're putting significant effort these days to try to clean up some of the really bad code which has accumulated over the years that no-one dares touch anymore (this, crimewatch, POSes are getting some rethink Soon(tm)) because of the certain breakage said touching will cause.

That said, we can't please everybody at the same time, but we'll do our best to address your concerns wrt. the change in functionality here. We've already made a few changes to address stuff raised in this thread, but I'll leave it to CCP Habakuk and Grayscale to detail those. Keep watching this space....

Cheers.

Ok, I've finally read through the whole thread. Is the following a fair summary of the issues and questions raised ?

* Granularity of access, i.e. the ability to offer access to the SMB and FH separately to either corp or fleet or both.
* Visual organization, i.e. a single click to view groups of items.
* Divisional security, i.e. the ability to have a (semi-)private section and "public" section, so far accomplished with corp roles.
* Emergency fitting problem. i.e. the ability to Ctrl+A -> drag everything over the fitting screen because OMGTHEYREGANKINGMEOHSHITOHSHITOHSHIT.
* Max pilots using fitting service as once. This is actually a red herring and in any case not something I've changed, but was raised, so lets include it anyway. Maybe the restriction should be changed. No promises though.
* Question about scannability. Are FH contents scannable? Should they be?
* Question regarding loot drops. Does FH content drop as loot? Should it?

Am I missing something?

I guess I'll have to double check, but I assumed the ability to filter items would take care of most "organization issues".

Fleet hangars and ship maintenance arrays on ships both now have "allow fleet member use" and "allow corp member use" in the inventory UI

Can Industrialist get some kind of anti-scan module? I mean some kind of counter would be nice. Or is the answer going to be the same old fit a tank fluff?

What's the problem? Do you really just want Industrial ganking to be mini-pos bashing?

I do not believe that this is anyway derailing the thread. This has very important implications for a large amount of players and should be discussed.

You are the one going off topic with your name calling.

Yes the Orca and other Industrialist can fit a tank. I'm not asking for any kind of HP buff. Just some kind of way to counter scanning. Some new ways to play, since CCP is changing things.

Really, with the addition of the 5 new containers sizing 1000m3 to 250km3 there is no point in having corp hangers/fleet hangers other than the fact that they are now Fleet accessible in a more intuitive fashion.

Being unscannable was nice, but apparently deemed an unintended mechanic. Adapt or die.